fortimail vm01

(PING) Check whether showmount-e aa is effective 11 disable firewall and sefenforce 12 mkdir/data/xen/create a directory 13 create a 4G file to install the VM Dd If =/dev/Zero of =/data/xen/vm01.img BS = 1 m COUNT = 4096 14. Install virtual machines Virt-install-N vm01-r 256-F/data/xen/vm01.img -- nographics-l NFS: 192.168.1.100:/Media -N: followed by the Virtua

One memory CPU is adjusted by 1.1 to increase the VM memory 1 [[email protected] ~] # Virsh shutdown vm01-centos6.8 2 [[email protected] ~] # Virsh edit vm01-centos6.8 3 ...... 4 1 virsh setmaxmem vm01-centos6.8 4G # need to shut down this VM 2 VM memory adjustment 3 virsh setmem uakvm2 2g -- config # adjust 4 virsh setmem uakvm2 2G # adjust the status of bootQc

Use virt-install to create an xen Virtual Machine [root @ gmnode14 vm01-CentOS-5.5] # virt-install-N vm01-CentOS-5.5-r 1024 -- vcpus = 4-F vm01-CentOS-5.5.img-s 20 -- nographic-l NFS: 10.10.113.14:/opt/centos/mirrors/5.5 ------------------------- Virt-install Parameter Parsing: -NVm01-CentOS-5.5#Virtual Machine name, here our name is

Clone a KVM Host Machine 1.1 to view VM configurations 1 [[email protected] ~] # Cat/etc/libvirt/qemu/vm01-centos6.8.xml 2 ............ 3 [[email protected] ~] # Ll/data/images/# VM disk file 4 total 1.3G 5-RW -------. 1 qemu 21G May 27 vm01-centos6.8.img 6 7 [[email protected] ~] # Virsh list -- all # Virtual Machine name 8 id name state 9 -------------------------------------------------- 10-

-2-xen-amd64 root=/dev/mapper/vpsee-root ro console=tty0Module/initrd.img-2.6.26-2-xen-amd64...After restarting the system, check to see if the Xen kernel and Xen are started: # reboot # Uname-r2.6.26-2-xen-amd64 # XM ListName ID Mem Vcpus State time (s)Domain-0 0 256 2 R-----9.3Create and install GuestIf the operating system of the Xen kernel is considered host, then the operating system running on the host can be viewed as guest. First build a directory to store all the guest operating system

overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:1701456 (1.6 mib) TX bytes:7347870 (7.0 MiB)interrupt:251 Base address:0x2000Lo Link encap:local Loopbackinet addr:127.0.0.1 mask:255.0.0.0Inet6 addr::: 1/128 scope:hostUp loopback RUNNING mtu:16436 metric:1RX packets:334 errors:0 dropped:0 overruns:0 frame:0TX packets:334 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:23680 (23.1 KiB) TX bytes:23680 (23.1 KiB)virbr0Link encap:ethernet hwaddr 00:00:00:00:00:00ine

pool2 V2V migration 2.1 preparation source host: vm01-centos6.8 source VM name: KVM-host 172.24.8.32 destination host: kvm-host-2 172.24.8.41 Virtual Machine name after migration: vm01-cloud-centos6.8 source + Destination hosts all need to refer to creating the same virtualized storage pool. View the VM status of the target host. Note: The virt-v2v only supports static migration, you must stop the VM to be

= 2Splashimage = (hd0, 0)/grub/splash.xpm.gzHiddenmenuTitle CentOS (2.6.18-128.2.1.el5xen)Root (hd0, 0)Kernel/xen.gz-2.6.18-128.2.1.el5Module/vmlinuz-2.6.18-128.2.1.el5xen ro root =/dev/VolGroup00/LogVol00Module/initrd-2.6.18-128.2.1.el5xen.imgTitle CentOS (2.6.18-128.1.16.el5)Root (hd0, 0)Kernel/vmlinuz-2.6.18-128.1.16.el5 ro root =/dev/VolGroup00/LogVol00Initrd/initrd-2.6.18-128.1.16.el5.img After the system is restarted, check whether the kernel is Xen: # Uname-r2.6.18-128.2.1.el5xenCheck wh

To view the partitioning of a vm01 virtual machine [[emailprotected]~]#virt-filesystems-dvm01/dev/sda1/dev/ Volgroup/lv_root mount the/DEV/SDA1 partition of the VM01 virtual machine to/mnt/1[[emailprotected]~]#guestmount-a/ Home/kvm/vm01/vm01.img-m/dev/sda1--rw/mnt/1[[emailprotected]~]#cd /mnt/1[[emailprotected]1]#lsco

system is restarted, check whether the kernel is Xen: # Uname-r2.6.18-128.2.1.el5xenCheck whether Xen has been started: #/Usr/sbin/xm listName ID Mem (MiB) VCPUs State Time (s)Domain-0 0 1220 2 r ----- 3214.1Create and install guestIf you think of the operating system of the running Xen kernel as the host, the operating system running on the host can be considered as the guest. Create a directory to store the images, vm01.img, and vm02.img of all the

Detailed description of the dr mode of lvs I. Environment Introduction Three virtual machines are used for lvs Server Load balancer experiments. vm01 is a server Load balancer with only one Nic. vm02 and vm03 are real web servers. vm01eth0:192.168.46.131vip:192.168.46.200vm02eth1:192.168.46.130vm03eth1:192.168.46.134 IIHow the lvs dr mode works Official principles: ctor receives user requests, selects a realserver Based on the server Load balancer al

Three virtual machines to do LVS load balancing experiment, VM01 is load balancer, only a network card, VM02 and vm03 are real Web servers, their relationship, here and the NAT mode of the difference between the LVS is the server IP address can be in a network segment. This is the legendary Tun tunnel model. Vm01 eth0:192.168.1.200 vip:192.168.1.30 Vm02 eth1:192.168.1.201 Vm03 eth1:192.168.1.202 Fir

Test neutron of openstack (JUNO) I tested the company's openstack environment over the past two days because the environment was built by other colleagues. I am only responsible for the relevant tests, and one server is installed independently. Controller node, the other two servers are installed with network node + compute node. The general environment is as follows: The Internet IP address segment is 192.168.1.0/24, of which 192.168.1.100 ~ 192.168.1.200 is the allocation range of floatingip,

Three virtual machines to do LVS load balancing experiment, VM01 is load balancer, VM02 and vm03 are real Web servers, their relationship Vm01 eth0:192.168.1.200 eth1:192.168.87.140 (where the 192.168.87.0 network segment can be connected to the extranet) vip:192.168.87.30 Vm02 eth1:192.168.1.201 (gateway:192.168.1.200) Vm03 eth1:192.168.1.202 (gateway:192.168.1.200) First, Load balancer installati

dom0_mem = 256 MModule/vmlinuz-2.6.26-2-xen-amd64 root =/dev/mapper/vpsee-root ro console = tty0Module/initrd. img-2.6.26-2-xen-amd64...After the system is restarted, check whether the Xen kernel is enabled and whether the Xen is started: # Reboot # Uname-r2.6.26-2-xen-amd64 # Xm listName ID Mem VCPUs State Time (s)Domain-0 0 256 2 r ----- 9.3Create and install guestIf you think of the operating system of the running Xen kernel as the host, the operating system running on the host can be consid

)After the installation is successful, check whether the Xen kernel has been installed, and add dom0_mem = 256 M to the kernel to limit the Xen Dom0 memory to prevent dom0 from consuming the memory: # Vi/boot/grub/menu. lst ...Title Xen 3.2-1-amd64/Debian GNU/Linux, kernel 2.6.26-2-xen-amd64Root (hd0, 0)Kernel/xen-3.2-1-amd64.gz dom0_mem = 256 MModule/vmlinuz-2.6.26-2-xen-amd64 root =/dev/mapper/vpsee-root ro console = tty0Module/initrd. img-2.6.26-2-xen-amd64...After the system is restarted, ch

Solve the problem that the KVM host cannot connect to the client through the console I. Problem description: The KVM host cannot connect to the client through the console, and it does not move here. # Virsh console vm01 Connected to domain vm01 Escape character is ^] Add virsh console support for KVM clients Ii. Solution: Use vnc or host desktop to enter the client vm01